SGI Freeware 2002 November

home *** CD-ROM | disk | FTP | other *** search

/ SGI Freeware 2002 November / SGI Freeware 2002 November - Disc 2.iso / dist / fw_hylafax.idb / usr / freeware / catman / u_man / cat1 / hfaxd.Z / hfaxd

Wrap

Text File | 2002-07-08 | 35KB | 719 lines

HFAXD(${MANNUM1_8}) HFAXD(${MANNUM1_8}) NNAAMMEE hfaxd - _H_y_l_a_F_A_X client-server protocol server SSYYNNOOPPSSIISS $${{LLIIBBEEXXEECC}}//hhffaaxxdd [ --dd ] [ --qq _d_i_r ] [ --oo _p_o_r_t ] [ --OO ] [ --ii _p_o_r_t ] [ --II ] [ --ss _p_o_r_t ] [ --SS ] DDEESSCCRRIIPPTTIIOONN _h_f_a_x_d is the _H_y_l_a_F_A_X program that implements the server portion of: the (new) client-server protocol, the old client-server protocol previously implemented by the _f_a_x_d_._r_e_c_v program, and the Simple Network Paging Protocol (SNPP) used to sub mit message pager jobs to the IXO/TAP and UCP support. Additional client-server protocols are planned and _h_f_a_x_d is intended to be the ``carrier'' through which they are supported. _h_f_a_x_d is typically used in one of two ways; either as a standalone process that is started at system boot time to listen for client connections on one or more ports, or as a subservient process to the _i_n_e_t_d(${MANNUM1_8}) program. The two forms of use may however be combined so long as the same service is not provided both by the standalone _h_f_a_x_d and through _i_n_e_t_d. HHYYLLAAFFAAXX ((NNEEWW)) CCLLIIEENNTT--SSEERRVVEERR PPRROOTTOOCCOOLL SSUUPPPPOORRTT If _h_f_a_x_d is started with the --ii option it will service clients using the (new) _H_y_l_a_F_A_X client-server protocol. This protocol is strongly related to the Internet File Transfer Protocol (FTP); so much so in fact that FTP client programs that include support for ``quoted com mands'' may be used to communicate with _h_f_a_x_d using the new protocol. (It should also be possible to use FTP- aware World Wide Web browsers such as Mosaic and Netscape Navigator to access _H_y_l_a_F_A_X servers through the new proto col; but the current format for information returned in directory listings confuses them.) The _h_f_a_x_d server currently recognizes the following proto col requests; case is not distinguished. Entries marked with a can be used only when the client has established administrative privileges with ADMIN. RReeqquueesstt DDeessccrriippttiioonn ABOR abort previous command ACCT specify account (ignored) ADMIN specify password for administrative privileges ALLO allocate storage (vacuously) ANSWER request that call be answered APPE append to a file CDUP change to parent of current working directory CHMOD change mode of a file CHOWN change owner of a file CWD change working directory DELE delete a file DISABLE disable outbound use of modem ENABLE enable outbound use of modem HELP give help information FILEFMT specify/query format for returning file status FORM specify data transfer _f_o_r_m_a_t IDLE set idle-timer (in seconds) JDELE delete done or suspended job JINTR interrupt job JKILL kill job JNEW create new job JOB set/query current job JOBFMT specify/query format for returning job status JPARM specify/query job state parameter JREST reset current job state JSUBM submit job to scheduler JSUSP suspend job from scheduling JWAIT wait for job to complete JGDELE delete group of jobs JGKILL kill group of jobs JGINTR interrupt group of jobs JGNEW place current job in a new job group JGPARM set state parameter in a group of jobs JGREST reset current state for a group of jobs JGRP set/query current job group JGSUBM submit group of jobs to scheduler JGSUSP suspend group of jobs from scheduling JGWAIT wait for group of jobs to complete LIST list files in a directory MDTM show last modification time of file MODE specify data transfer _m_o_d_e MDMFMT specify/query format for returning modem status NLST give name list of files in directory NOOP do nothing PASS specify password PASV prepare for server-to-server transfer PORT specify data connection port PWD print the current working directory QUIT terminate session RCVFMT specify/query format for returing received facsimile status REIN reinitiate server state REST restart incomplete transfer RETP retrieve the next page in a file RETR retrieve a file SHUT schedule server shutdown SITE non-standard commands (see next section) SIZE return size of file STAT return status of server or file STOR store a file STOT store a temporary file with a unique name STOU store a file with a unique name STRU specify data transfer _s_t_r_u_c_t_u_r_e SYST show operating system type of server system TYPE specify data transfer _t_y_p_e TZONE specify timezone handling for dates and times USER specify user name VRFY verify dialstring handling and/or least-cost routing The following non-standard or experimental commands are supported through the SITE request. RReeqquueesstt DDeessccrriippttiioonn ADDMODEM add/configure new modem for use ADDUSER add client access control entry CONFIG send configuration parameter setting to server DELMODEM deconfigure/remove modem DELUSER remove client access control entry TRIGGER register realtime event trigger HELP give help information, e.g., SITE HELP In addition FTP requests that are specified in Internet RFC 959 but not listed here are recognized, but not imple mented. The _h_f_a_x_d server will abort an active data transfer only when the ABOR command is preceded by a Telnet "Interrupt Process" (IP) signal and a Telnet "Synch" signal in the command Telnet stream, as described in Internet RFC 959. If a STAT command is received during a data transfer, pre ceded by a Telnet IP and Synch, transfer status will be returned. OOLLDD CCLLIIEENNTT--SSEERRVVEERR PPRROOTTOOCCOOLL SSUUPPPPOORRTT If _h_f_a_x_d is started with the --oo option it will service clients using the old _H_y_l_a_F_A_X client-server protocol that was used in distributions prior to the 4.0 release. Note however that this support is only available if _h_f_a_x_d is compiled with the support enabled. Emulation of the old protocol is important for supporting non-UNIX clients such as the WinFlex client for Windows systems and the MacFlex client for Macintosh systems. It is strongly recommended however that unless you need to support these old-style clients that you not enable sup port for the old protocol because of the inherent misde sign of this protocol. SSIIMMPPLLEE NNEETTWWOORRKK PPAAGGIINNGG PPRROOTTOOCCOOLL ((SSNNPPPP)) SSUUPPPPOORRTT If _h_f_a_x_d is started with the --ss option it will service clients using the Simple Network Pager Protocol (SNPP) as specified in RFC 1861 (which obsoletes RFC 1645). The _h_f_a_x_d server currently recognizes the SNPP protocol requests listed below. Requests marked with a are non- standard extensions to RFC 1861 that may be added to SNPP at some future time. Case is not distinguished and only the first four characters of requests are used in identi fying commands. RReeqquueesstt DDeessccrriippttiioonn 2WAY preface a 2-way transaction ABOR abort previous command ACKR set read acknowledgement handling for subsequent requests ALER set the alter-level for subsequent requests CALL set the caller-ID for subsequent requests COVE set the alternate coverage area for subsequent requests DATA specify a multi-line message EXPT set the expiration time for subsequent requests HELP give help information HOLD set the time at which subsequent requests are to be delivered KTAG kill a previously submitted request LEVE set the service level for subsequent requests LOGI login to server MCRE specify multiple response text and code MESS specify a single-line message MSTA return the status of a previously submitted request NOQU diable message queueing PAGE specify the destination pager PING locate/validate a pager QUIT terminate session RESE reset server state RTYP set the reply type code for subsequent requests SEND send message(s) SITE site-specific commands (see next section) STAT return server status SUBJ set the message text for subsequent requests The _h_f_a_x_d server will abort an active SEND operation when an ABOR command is preceded by a Telnet "Interrupt Pro cess" (IP) signal and a Telnet "Synch" signal in the com mand Telnet stream. The following non-standard or experimental commands are also supported through the SITE request. RReeqquueesstt DDeessccrriippttiioonn FROMUSER specify the sender's identity IDLE set idle-timer (in seconds) JPARM query job parameter status JQUEUE control whether or not job is queued LASTTIME set the time to terminate an unfinished job MAILADDR set the e-mail address to use for notification MAXDIALS set the maximum number of times to dial the phone MAXTRIES set the maximum number of times to try sending the page MODEM set the modem or class of modems to use NOTIFY set the e-mail notification RETRYTIME set the time to delay between job retries SCHEDPRI set the scheduling priority for the job HELP give help information, e.g., SITE HELP Note that _h_f_a_x_d requires that SNPP clients login first with the LOGI directive while RFC 1861 permits clients to submit pages anonymously. CCLLIIEENNTT AACCCCEESSSS CCOONNTTRROOLL _h_f_a_x_d controls client access according to the information in the file $${{SSPPOOOOLL}}//eettcc//hhoossttss..hhffaaxxdd. This file defines the set of users and machines that may receive service and, optionally, defines password challenges to use in authenticating clients. Clients may be permitted access to services with or without a password challenge. Access may also be restricted based on the host machine that a request for service originates from. Consult _h_o_s_t_s_._h_f_a_x_d(${MANNUM4_5}) for information on the format and content of this file. The SITE ADDUSER protocol request is provided for adding new users to a server (available only to clients with administrative privi leges). Server resources are controlled based on clients' identi ties. Jobs and documents, both received and submitted, are protected by the server. Typically clients are per mitted access to anything they own or that is publicly accessible. There are also administrative privileges that clients may acquire and which permit them wide access to objects that reside on the server. A complete client-server protocol specification is still outstanding. _h_f_a_x_d operates with its root directory set to the top of the _H_y_l_a_F_A_X spooling area; ${SPOOL}. This is done so that clients see a virtual file hierarchy that is completely contained within the _H_y_l_a_F_A_X operating environment on the server machine. Administrators however must be aware of this action when specifying files in the _h_f_a_x_d configura tion file: absolute pathnames relative to the root of the spooling should be used to specify filenames. SSEERRVVEERR AACCCCEESSSS CCOONNTTRROOLL The file $${{SSPPOOOOLL}}//eettcc//sshhuuttddoowwnn, when present, specifies when to restrict access to a server machine. When this file is present and contains valid information _h_f_a_x_d will permit only users with administrative privileges to access the server. Any other users that request service will be denied access and negative server responses will include any shutdown message specified in the shutdown file. Con sult _h_y_l_a_f_a_x_-_s_h_u_t_d_o_w_n(${MANNUM4_5}) for information on the format and content of this file. The SHUT protocol request can be used to schedule a server shutdown; it is available only to clients with administra tive privileges. To make a shutdown server available again the shutdown file can be deleted with the DELE pro tocol request (_t_h_i_s _i_s _t_o _b_e _r_e_p_l_a_c_e_d _w_i_t_h _a_n _`_`_u_n_s_h_u_t_'_' _p_r_o_t_o_c_o_l _r_e_q_u_e_s_t _s_o _t_h_a_t _i_m_p_l_e_m_e_n_t_a_t_i_o_n _d_e_t_a_i_l_s _a_r_e _n_o_t _p_a_r_t _o_f _t_h_e _p_r_o_t_o_c_o_l). CCOONNFFIIGGUURRAATTIIOONN FFIILLEESS _h_f_a_x_d reads configuration information from the file $${{LLIIBB DDAATTAA}}//hhffaaxxdd..ccoonnff each time a new server process is started (i.e. for each new client). This file uses the same con ventions used by other _H_y_l_a_F_A_X configuration files; as described in _h_y_l_a_f_a_x_-_c_o_n_f_i_g(${MANNUM4_5}). The following configuration parameters are recognized; items marked ``(SNPP)'' are used only by the SNPP support. TTaagg TTyyppee DDeeffaauulltt DDeessccrriippttiioonn FaxContact string _s_e_e _b_e_l_o_w contact address to show in help text FileFmt string _s_e_e _b_e_l_o_w format string for file status results IdleTimeout integer 900 client idle timeout in seconds JobFmt string _s_e_e _b_e_l_o_w format string for job status results KillTimeMap string _s_e_e _b_e_l_o_w mapping from service level to job kill time (SNPP) LogFacility string daemon _s_y_s_l_o_g facility name for tracing messages MaxAdminAttempts integer 5 maximum admin attempts before disconnecting MaxConsecutiveBadCmds integer 10 maximum invalid commands before disconnecting MaxIdleTimeout integer 7200 maximum client idle timeout permitted MaxLoginAttempts integer 5 maximum login attempts before disconnecting MaxMsgLength integer 128 maximum pager message length (SNPP) ModemFmt string _s_e_e _b_e_l_o_w format string for modem status results PagerIDMapFile string ${SPOOL}/etc/pagermap name of file for mapping pager IDs (SNPP) PriorityMap string _s_e_e _b_e_l_o_w mapping from service level to job priority (SNPP) RcvFmt string _s_e_e _b_e_l_o_w format string for received facsimile status results RetryTimeMap string _s_e_e _b_e_l_o_w mapping from service level to job retry time (SNPP) ServerTracing integer 1 server tracing control vector ShutdownFile string ${SPOOL}/etc/shutdown name of shutdown control file UserAccessFile string ${SPOOL}/etc/hosts.hfaxd name of access control file XferLogFile string ${SPOOL}/etc/clientlog name of file for logging client data transfers The configuration parameters are explained below: FFaaxxCCoonnttaacctt The e-mail address to display as a point of con tact in the help text returned to a client in response to the HELP or SITE HELP commands. By default this is ``FaxMaster@_h_o_s_t_n_a_m_e'', where _h_o_s_t_n_a_m_e is the fully qualified name for the machine where the server is running. FFiilleeFFmmtt The format string to use when returning file status information with the LIST and STAT com mands. Formats are specified using _p_r_i_n_t_f(3S) style conventions but using the field identi fiers listed below. Each item can include field width, precision, left-justification, 0-filling, etc. just as for _p_r_i_n_t_f; e.g. %-8p for an 8-character wide, left-justified, blank-padded field containing the file protection flags. FFoorrmmaatt DDeessccrriippttiioonn a Last access time c Creation time d Device number (octal) f Filename g Group identifier (decimal) i Inode number (decimal) l Link count (decimal) m Last modification time o Owner (based on file GID) p Fax-style protection flags (no group bits) q UNIX-style protection flags r Root device number (octal) s File size in bytes (decimal) u User identifier (decimal) The default format string is ``%-7p %3l %8o %8s %-12.12m %.48f''. It is recommended that all items include a field width so that client applications that construct headers from the format string can constrain the width of column title strings. IIddlleeTTiimmeeoouutt The initial/default timeout to use in timing out idle clients. This value defines the maximum amount of time (in seconds) that _h_f_a_x_d will wait for a command from a client before terminating the connection. Unprivileged clients may alter the idle timeout up to the value of _M_a_x_I_d_l_e_T_i_m_e_ _o_u_t; privileged clients may set the timeout to any value. JJoobbFFmmtt The format string to use when returning job sta tus information for jobs in the sseennddqq and ddoonneeqq directories. Formats are specified using _p_r_i_n_t_f(3S) style conventions but using the field identifiers listed below. Each item can include field width, precision, left-justification, 0-filling, etc. just as for _p_r_i_n_t_f; e.g. %-3j for a 3-character wide, left-justified, blank- padded field containing the job state. FFoorrmmaatt DDeessccrriippttiioonn A Destination SubAddress B Destination Password C Destination company name D Total # dials/maximum # dials E Desired signalling rate F Client-specific tagline format string G Desired min-scanline time H Desired data format I Client-specified scheduling priority J Client-specified job tag string K Desired use of ECM L Destination geographic location M Notification e-mail address N Desired use of private tagline (one-character symbol) O Whether to use continuation cover page (one-character symbol) P # pages transmitted/total # pages to transmit Q Client-specified minimum acceptable signalling rate R Destination person (receiver) S Sender's identity T Total # tries/maximum # tries U Page chopping threshold (inches) V Job done operation W Communication identifier X Job type (one-character symbol) a Job state (one-character symbol) b # consecutive failed tries c Client machine name d Total # dials e Public (external) format of dialstring f # consecutive failed dials g Group identifier h Page chop handling (one-character symbol) i Current scheduling priority j Job identifier k Job kill time l Page length in mm m Assigned modem n E-mail notification handling (one-character symbol) o Job owner p # pages transmitted q Job retry time (MM::SS) r Document resolution in lines/inch s Job status information from last failure t Total # tries attempted u Maximum # tries v Client-specified dialstring w Page width in mm x Maximum # dials y Total # pages to transmit z Time to send job The default format string is ``%-4j %3i %1a %6.6o %-12.12e %5P %5D %7z %.25s''. This string constrains each status line to be less than 80 characters. It is recommended that all items include a field width so that client applica tions, such as _f_a_x_s_t_a_t(1) that construct headers from the format string can constrain the width of column title strings. KKiillllTTiimmeeMMaapp The mapping from SNPP service level (0-11) to job expiration time (kill time). A mapping is specified as a string of space-separate numbers where each value is the number of minutes to permit a job to run. The default mapping is ``5 5 5 15 60 240 720 1440 1440 1440 1440 1440'' which expires a job in 5 minutes for service levels 0-2, 15 minutes for level three, 60 min utes for level four, etc. LLooggFFaacciilliittyy The symbolic name for the _s_y_s_l_o_g(3) facility to use when logging error messages and informa tional/debugging messages requested through the SSeerrvveerrTTrraacciinngg parameter. The list of facility names is found in the system include file <<ssyyss lloogg..hh>>; comparisons are case-insensitive. MMaaxxAAddmmiinnAAtttteemmppttss The maximum number of unsuccessful attempts gain adminstrative privileges with the ADMIN command that _h_f_a_x_d will permit a client before terminat ing the connection. Note that the count of attempts is reset if/when the client success fully gains administrative privileges. MMaaxxCCoonnsseeccuuttiivveeBBaaddCCmmddss The maximum number of consecutive unrecognized, unimplemented, syntactically incorrect, or oth erwise unacceptable commands to permit a client before terminating the connection. This control has two purposes: to handle naive or malicious clients from sending long streams of nonsense commands to a server, and to insure that clients are forcibly terminated when a server is marked shutdown. MMaaxxIIddlleeTTiimmeeoouutt The maximum value that a client may set the idle timeout to. This value is not enforced if the client has administrative privileges. MMaaxxLLooggiinnAAtttteemmppttss The maximum number of unsuccessful attempts to login with the USER and PASS commands that _h_f_a_x_d will permit a client before terminating the con nection. MMaaxxMMssggLLeennggtthh The maximum number of characters to accept in a pager message specified with the DATA or MESS commands. Messages longer than this value are rejected. MMooddeemmFFmmtt The format string to use when returning modem status information for modems listed in the ssttaa ttuuss directory. Formats are specified using _p_r_i_n_t_f(3S) style conventions but using the field identifiers listed below. Each item can include field width, precision, left-justification, 0-filling, etc. just as for _p_r_i_n_t_f; e.g. %-8h for an 8-character wide, left-justified, blank- padded field containing the name of the host the server is running on. FFoorrmmaatt DDeessccrriippttiioonn h Server hostname l Local identifier string m Canonical modem name n FAX phone number r Maximum pages that can be received in a single call s Status information string t Server and session tracing levels (xxxxx:yyyyy) v Modem speaker volume as one-character symbol z A ``*'' if a _f_a_x_g_e_t_t_y(${MANNUM1_8}) process is running; otherwise `` '' (space) The default format string is ``Modem %m (%n): %s''. PPaaggeerrIIDDMMaappFFiillee The absolute pathname of the file that contains directions for mapping pager identifiers to IXO/TAP or UCP service providers (and optionally a pager identification number). Consult _p_a_g_e_r_m_a_p(${MANNUM4_5}) for information on the format and content of this file. (Note that absolute pathnames are relative to the root of the spooling area). PPrriioorriittyyMMaapp The mapping from SNPP service level (0-11) to job scheduling priority. A mapping is specified as a string of space-separate numbers where each value is the priority to assign to a job. The default mapping is ``63 127 127 127 127 127 127 127 127 127 127 127'' which assigns a high pri ority to service level zero and normal (default) priority to all other service levels. RRccvvFFmmtt The format string to use when returning status information for received facsimile in the rreeccvvqq directory. Formats are specified using _p_r_i_n_t_f(3S) style conventions but using the field identifiers listed below. Each item can include field width, precision, left-justification, 0-filling, etc. just as for _p_r_i_n_t_f; e.g. %-3b for a 3-character wide, left-justified, blank- padded field containing the signalling rate. FFoorrmmaatt DDeessccrriippttiioonn a SubAddress received from sender (if any) b Signalling rate used during receive d Data format used during receive e Error description if an error occurred during receive f Document filename (relative to the rreeccvvqq directory) h Time spent receiving document (HH:MM:SS) l Page length in mm m Fax-style protection mode string (``-rwxrwx'') n File size (number of bytes) o File owner p Number of pages in document q UNIX-style protection flags r Resolution of received data s Sender identity (TSI) t Compact representation of the time when the receive happened w Page width in mm z A ``*'' if receive is going on; otherwise `` '' (space) The default format string is ``%-7m %4p%1z %-8.8o %14.14s %7t %f''. This string constrains each status line to be less than 80 characters. It is recommended that all items include a field width so that client applications, such as _f_a_x_s_ _t_a_t(1) that construct headers from the format string can constrain the width of column title strings. RReettrryyTTiimmeeMMaapp The mapping from SNPP service level (0-11) to job retry time. A mapping is specified as a string of space-separate numbers where each value is the number of seconds to delay between delivery attempts. A value of zero causes retries to be scheduled using the default algo rithm used by the _H_y_l_a_F_A_X job scheduler. The default mapping is ``30 60 60 180 0 0 0 0 0 0 0 0'' which retries a level 0 job after a 30 sec ond delay, levels 1 and 2 after 60 seconds, level 3 after 3 minutes, and other jobs are retried according to the usual scheduling algo rithm. SSeerrvveerrTTrraacciinngg A number that controls the generation of tracing information by a server. _a_r_e_a_s that are indi vidually controlled. To enable tracing of mul tiple areas of operation, the flag associated with each area should be bit-or'd to form the value for this tag. FFllaagg DDeessccrriippttiioonn 1 (0x00001) General server operation 2 (0x00002) Client-server protocol requests and responses 4 (0x00004) File transfers from client to server 8 (0x00008) File transfers from server to client 16 (0x00010) Client logins 32 (0x00020) All network connections 64 (0x00040) FIFO messages to and from _f_a_x_q(${MANNUM1_8}) 128 (0x00080) TIFF Library errors and warnings 256 (0x00100) Configuration file processing Tracing messages are directed to _s_y_s_l_o_g(3) using the _f_a_c_i_l_i_t_y specified with the LLooggFFaacciilliittyy con figuration parameter. Note that _s_y_s_l_o_g_d(${MAN NUM1_8}) must be configured to capture _f_a_c_i_l_ _i_t_y_._i_n_f_o, _f_a_c_i_l_i_t_y_._d_e_b_u_g, _f_a_c_i_l_i_t_y_._w_a_r_n_i_n_g, and _f_a_c_i_l_i_t_y_._e_r_r messages. SShhuuttddoowwnnFFiillee The absolute pathname of the server shutdown file; see _h_y_l_a_f_a_x_-_s_h_u_t_d_o_w_n(${MANNUM4_5}) for information on the format and content of this file. (Note that absolute pathnames are rela tive to the root of the spooling area). UUsseerrAAcccceessssFFiillee The absolute pathname of the user access control file; see _h_o_s_t_s_._h_f_a_x_d(${MANNUM4_5}) for informa tion on the format and content of this file. (Note that absolute pathnames are relative to the root of the spooling area). XXffeerrLLooggFFiillee The absolute pathname of the file to use for logging client-server file transfers (when enabled through the SSeerrvveerrTTrraacciinngg parameter). (Note that absolute pathnames are relative to the root of the spooling area). OOPPTTIIOONNSS --qq _d_i_r The specified directory is treated as the spool ing area. The default spooling area, _$_{_S_P_O_O_L_}, is defined at the time the software is built. --dd Stop _h_f_a_x_d from _d_e_t_a_c_h_i_n_g itself from the con trolling terminal. This option is normally used only when running _h_f_a_x_d under a debugger or when _h_f_a_x_d is started up from the _i_n_e_t_d(${MANNUM1_8}) process. --ii _p_o_r_t Listen on the specified _p_o_r_t for service requests and respond with the (new) client- server protocol. The port may be specified either symbolically, e.g. ``hylafax'' or numeri cally. This flag may be specified multiple times to request service on multiple different ports. --oo _p_o_r_t Listen on the specified _p_o_r_t for service requests and respond with the old client-server protocol. The port may be specified either sym bolically, e.g. ``fax'' or numerically. This flag may be specified multiple times to request service on multiple different ports. --ss _p_o_r_t Listen on the specified _p_o_r_t for service requests and respond with the Simple Network Paging (SNPP) protocol. The port may be speci fied either symbolically, e.g. ``snpp'' or numerically. This flag may be specified multi ple times to request service on multiple differ ent ports. --II Service the (new) client-server protocol using the standard input and output. This option is useful when _h_f_a_x_d is started up by _i_n_e_t_d(${MAN NUM1_8}). --OO Service the old client-server protocol using the standard input and output. This option is use ful when _h_f_a_x_d is started up by _i_n_e_t_d(${MAN NUM1_8}). --SS Service the Simple Network Paging (SNPP) proto col using the standard input and output. This option is useful when _h_f_a_x_d is started up by _i_n_e_t_d(${MANNUM1_8}). DDIIAAGGNNOOSSTTIICCSS Diagnostics generated by _h_f_a_x_d are logged using _s_y_s_l_o_g(3). FFIILLEESS ${LIBDATA}/hfaxd.conf server configuration file ${SPOOL} spooling area ${SPOOL}/FIFO for submitting the job ${SPOOL}/sendq where job description is placed ${SPOOL}/sendq/seqf for assigning job identifiers ${SPOOL}/docq/seqf for assigning document identifiers ${SPOOL}/tmp temporary location of job-related files ${SPOOL}/docq where document files are placed ${SPOOL}/recvq where received facsimile are found ${SPOOL}/archive where archived jobs are placed ${SPOOL}/log for server log files ${SPOOL}/client for FIFO files used in communicating with _f_a_x_q ${SPOOL}/status for server status information ${SPOOL}/config._d_e_v_i_c_e for returning server status ${SPOOL}/etc/hosts.hfaxd host access control list ${SPOOL}/etc/shutdown server shutdown control ${SPOOL}/etc/pagermap SNPP pager ID mapping file BBUUGGSS To be filled in. SSEEEE AALLSSOO _s_e_n_d_f_a_x(1), _s_e_n_d_p_a_g_e(1), _f_a_x_a_l_t_e_r(1), _f_a_x_r_m(1), _f_a_x_s_ _t_a_t(1), _f_a_x_q(${MANNUM1_8}), _s_y_s_l_o_g(3) _h_y_l_a_f_a_x_- _s_e_r_v_e_r(${MANNUM4_5}), _h_o_s_t_s_._h_f_a_x_d(${MANNUM4_5}), _s_t_a_ _t_u_s(${MANNUM4_5}), _h_y_l_a_f_a_x_-_s_h_u_t_d_o_w_n(${MANNUM4_5}), July 12, 1996 HFAXD(${MANNUM1_8})